postprocess: Add cronjob test c2rust-postprocess#1857
Conversation
Crocodoctopus
force-pushed
the
bg/add-postprocess-ci-test
branch
from
84808f3 to
3a95eb4
Compare
thedataking
changed the title
thedataking
changed the title
thedataking
left a comment
thedataking
left a comment
There was a problem hiding this comment.
Missing: using the Github cache action to restore and save c2rust-postprocessor entries on the cronjob or PR runs. If that's why the PR is marked draft, no worries.
Crocodoctopus
force-pushed
the
bg/add-postprocess-ci-test
branch
2 times, most recently
from
24ae5c6 to
1d7e507
Compare
|
Most of this is pretty hacked together, I'll address feedback as it stabilizes. |
Crocodoctopus
force-pushed
the
bg/add-postprocess-ci-test
branch
18 times, most recently
from
5a09690 to
918a280
Compare
Crocodoctopus
force-pushed
the
bg/add-postprocess-ci-test
branch
from
918a280 to
ab63ac0
Compare
|
Currently, the cronjob launches the same way as the c2rust-testsuite workflow to ensure the latter can access the former's cache (for testing). When the cronjob hits master, on-pr and on-push workflows should have access to that cache as well(?). Tests show c2rust-testsuite/run-testsuite is using cached data from the cronjob, which runs postprocess on Most real changes are in |
2 participants
Test PR
c2rust-postprocesstesting in CI.The basic idea is to run a daily cronjob running
c2rust-postprocessonjson-cwith a real API key and with--on-error keep-going, generating new cache entries. PR CI runners will run their postprocess tests with under cache only with--on-error warn. This will have the side effect that breaking changes toc2rust-postprocessthat still work under--on-error warnwill only become apparent during the daily cronjob.